Access node/gateway to access node/gateway layer-2 connectivity (end-to-end)

ABSTRACT

Systems, methods, and apparatus for providing end-to-end L2 connectivity, are described. The system includes satellites configured to transmit data packets. The system further includes a first non-autonomous gateway in communication with the satellites. The first non-autonomous gateway is configured to receive the data packets from the satellites at L1, generate virtual tagging tuples within L2 packet headers of the data packets, and transmit the data packets each including a virtual tagging tuple. The system further includes a L2 switch in communication with the first non-autonomous gateway. The L2 switch is configured to receive the virtually tagged data packets and transmit the virtually tagged data packets. Further, the system includes a second non-autonomous gateway in communication with the L2 switch. The second non-autonomous gateway configured to receive the virtually tagged data packets and transmit the virtually tagged data packets to an entity based on the virtual tagging tuple associated with each of the virtually tagged packets.

PRIORITY CLAIM

This application claims priority to U.S. Provisional Application No.61/170,359, entitled DISTRIBUTED BASE STATION SATELLITE TOPOLOGY, filedon Apr. 17, 2009, and also claims priority to U.S. ProvisionalApplication No. 61/254,553, entitled ACCESS NODE/GATEWAY TO ACCESSNODE/GATEWAY LAYER-2 CONNECTIVITY (END-TO-END), filed on Oct. 23, 2009,which are both incorporated by reference in their entirety for any andall purposes.

BACKGROUND

Satellite communications systems are becoming ubiquitous forcommunicating large amounts of data over large geographic regions. Intypical satellite communications systems, end consumers interface withthe systems through user terminals. The user terminals communicate, viaone or more satellites, with one or more gateways. The gateways may thenprocess and route the data to and from one or more networks according tovarious network protocols and tags processed at the network layer andabove (e.g., layers 3 and above of the Open System InterconnectionReference Model (OSI) stack).

While utilizing higher layers to route communications may providecertain features, such as enhanced interoperability, it may also limitcertain capabilities of the network. For example, routing limits thetypes of tags that can persist across multiple sub-networks. For theseand/or other reasons, it may be desirable to provide ground-segmentnetworking with enhanced functionality.

SUMMARY OF THE INVENTION

In one embodiment, a systems for providing end-to-end L2 connectivity,are described. The system includes satellites configured to transmitdata packets. The system further includes a first non-autonomous gatewayin communication with the satellites. The first non-autonomous gatewayis configured to receive the data packets from the satellites at L1,generate virtual tagging tuples within L2 packet headers of the datapackets, and transmit the data packets each including a virtual taggingtuple. The system further includes a L2 switch in communication with thefirst non-autonomous gateway. The L2 switch is configured to receive thevirtually tagged data packets and transmit the virtually tagged datapackets. Further, the system includes a second non-autonomous gateway incommunication with the L2 switch. The second non-autonomous gatewayconfigured to receive the virtually tagged data packets and transmit thevirtually tagged data packets to an entity based on the virtual taggingtuple associated with each of the virtually tagged packets.

In another embodiment, a method of providing end-to-end layer-2connectivity throughout a non-routed ground segment network connected toone or more satellites, is described. The method includes transmitting,by the one or more satellites, data packets, receiving, at a firstnon-autonomous gateway in communication with the one or more satellites.The data packets from the one or more satellites at layer-1 (L1) of theOSI-model. The method further includes generating, by the firstnon-autonomous gateway, a plurality of virtual tagging tuples within thelayer-2 (L2) packet headers of the data packets. The plurality of datapackets each include a virtual tagging tuple. The method furtherincludes receiving, at a L2 switch in communication with the firstnon-autonomous gateway, the plurality of virtually tagged data packets,transmitting, by the L2 switch, the plurality of virtually tagged datapackets, and receiving, by a second non-autonomous gateway incommunication with the L2 switch, the plurality of virtually tagged datapackets. Further, the method includes transmitting, by the secondnon-autonomous gateway, the plurality of virtually tagged data packetsto an entity based on the virtual tagging tuple associated with each ofthe plurality of virtually tagged packets.

In yet another embodiment, a machine-readable medium for providingend-to-end layer-2 connectivity throughout a non-routed ground segmentnetwork connected to one or more satellites, is described. Themachine-readable medium includes instructions for transmitting, by theone or more satellites, data packets, receiving, at a firstnon-autonomous gateway in communication with the one or more satellites.The data packets from the one or more satellites at layer-1 (L1) of theOSI-model. The machine-readable medium further includes instructions forgenerating, by the first non-autonomous gateway, a plurality of virtualtagging tuples within the layer-2 (L2) packet headers of the datapackets. The plurality of data packets each include a virtual taggingtuple. The machine-readable medium further includes instructions forreceiving, at a L2 switch in communication with the first non-autonomousgateway, the plurality of virtually tagged data packets, transmitting,by the L2 switch, the plurality of virtually tagged data packets, andreceiving, by a second non-autonomous gateway in communication with theL2 switch, the plurality of virtually tagged data packets. Further, themachine-readable medium includes instructions for transmitting, by thesecond non-autonomous gateway, the plurality of virtually tagged datapackets to an entity based on the virtual tagging tuple associated witheach of the plurality of virtually tagged packets.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the remaining portions of thespecification and the drawings wherein like reference numerals are usedthroughout the several drawings to refer to similar components. In someinstances, a sublabel is associated with a reference numeral to denoteone of multiple similar components. When reference is made to areference numeral without specification to an existing sublabel, it isintended to refer to all such multiple similar components.

FIG. 1 illustrates a typical satellite communications system having atypical gateway in communication with a routed network.

FIG. 2 shows an embodiment of a satellite communications system having anumber of user terminals in communication with a non-autonomous gatewayvia a satellite, according to various embodiments.

FIG. 3 shows an embodiment of a satellite communications system having auser terminal in communication with a non-autonomous gateway via asatellite, where the non-autonomous gateway is further in communicationwith nodes of a non-routed ground segment network using virtual taggingtuples, according to various embodiments.

FIG. 4A shows an embodiment of a satellite communications system usedfor communication between two clients over a non-routed ground segmentnetwork, according to various embodiments.

FIG. 4B shows an illustrative communication link for an enterprisecustomer in a system, like the one shown in FIG. 4A.

FIG. 4C shows an illustrative data flow through the communication linkof FIG. 4B.

FIG. 5, an embodiment of a non-autonomous gateway is shown as part of aportion of a non-routed ground segment network, according to variousembodiments.

FIG. 6 shows an embodiment of a communications system having multiplenon-autonomous gateways, like the non-autonomous gateway of FIG. 5, incommunication with a more detailed illustrative embodiment of a corenode, according to various embodiments.

FIG. 7 shows embodiments of various modules in communication with one ormore multilayer switches, according to various embodiments.

FIG. 8 shows an embodiment of an autonomous gateway, according tovarious embodiments.

FIG. 9 shows an embodiment of a satellite communications system thatdistributes autonomous gateways and non-autonomous gateways across anumber of geographically dispersed regions, according to variousembodiments.

FIG. 10 is a flow diagram illustrating a method of a satellitecommunications system having a user terminal in communication withanother user terminal via a satellite, where the non-autonomous gatewayis further in communication with nodes of a non-routed ground segmentnetwork using virtual tagging tuples, according to various embodiments.

FIG. 11 is a simplified block diagram illustrating the physicalcomponents of a computer system that may be used in accordance with anembodiment of the present invention.

DESCRIPTION

The ensuing description provides exemplary embodiment(s) only, and isnot intended to limit the scope, applicability or configuration of thedisclosure. Rather, the ensuing description of the exemplaryembodiment(s) will provide those skilled in the art with an enablingdescription for implementing an exemplary embodiment, it beingunderstood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope asset forth in the appended claims. Some of the various exemplaryembodiments may be summarized as follows.

In many typical satellite communications systems, end consumersinterface with the systems through user terminals. The user terminalscommunicate, via one or more satellites, with one or more gateways. Thegateways may then process and route the data to and from one or morenetworks according to various network protocols and tags processed atthe network layer and above (e.g., layers 3 and above of the Open SystemInterconnection Reference Model (OSI) stack).

For example, FIG. 1 illustrates a typical satellite communicationssystem 100. The satellite communications system 100 includes a number ofuser terminals 130 in communication with a gateway 115 via a satellite105. For example, a subscriber of satellite communications servicesdesires to access a web page using a browser. The subscriber's client160 (e.g., a client application running on customer premises equipmentcontrolled by the subscriber) may communicate an HTML request through arespective one of the user terminals 130. A user antenna 135 incommunication with the respective user terminal 130 communicates therequest to the satellite 105, which, in turn, sends the request to thegateway 115 through a provider antenna 125.

The gateway 115 receives the request at a base station 145 configured toservice that user terminal 130 and included within a satellite modemtermination system (SMTS) 140. The SMTS 140 sends the request data to arouting module 150, in communication with a gateway module 155. Therouting module 150 and gateway module 155 work together to determine andgenerate routing data for communicating the request data through arouted ground segment network 120. Typically, the gateway module 155 maybe a control plane application which sets up connectivity to the router.Even where actual routing is not done by the gateway module 155,components of the gateway 115 may implement routing functions.

As used herein, a “routed network” refers to a network having a numberof routers, configured to use protocols at layer-3 and above of the OSIstack (e.g., or substantially equivalent types of protocols) to routedata through the network. The “routing module,” as used herein, isintended to broadly include any type of network device configured toroute at layers 3 and above of the OSI stack (e.g., or providesubstantially similar network layer functionality). Particularly,routing is intended to be distinguished from switching (e.g., at layer 2of the OSI stack (e.g., or substantially similar functionality), as willbecome more clear from the description below.

While utilizing higher layers to route communications may providecertain features, such as enhanced interoperability, it may also limitcertain capabilities of the network. As one exemplary limitation, ateach node where a layer-3 routing decision is made, determining theappropriate routing may involve parsing packet headers, evaluatingparsed header information against routing tables and port designations,etc. These steps may limit the amount and type of traffic that can besent over the network, as well as the protocols available for transporton the network.

In another exemplary limitation, at each router, layer-2 headers aretypically stripped off and replaced with other tags to identify at leastthe next routing of the data through the network. As such, it isimpossible to maintain a single network between routed terminals. Inother words, a packet which is generated at one LAN, passes through oneor more routers (i.e., at layer-3 or above) and is received at anotherLAN, will always be considered to be received from a different network.Accordingly, any benefit of a single network configuration isunattainable in a layer-3 routed network. For example, tags forsupporting proprietary service provider networks, Multiprotocol LabelSwitching (MPLS), and/or other types of networks are impossible tomaintain across large geographic regions (e.g., multiple LANs, WANs,subnets, etc.) of a routed ground segment network 120.

In the illustrative example, internet protocol (IP) and/or other tagsare used to route the request data to an appropriate IP address for usein satisfying the subscriber's request. When a response to the requestis received by the routed ground segment network 120, layer-3 and/orhigher-layer tags are again used to route the response data through thenetwork to the appropriate base station 145 in the appropriate gateway115. The base station 145 then communicates the response data to theclient 160 via the provider antenna 125, the satellite 105, thesubscriber antenna 135, and the user terminal 130.

Embodiments address these limitations of the routed ground segmentnetwork 120 in various ways, for example, through the use of core nodes.FIG. 2 shows an embodiment of a satellite communications system 200having a number of user terminals 130 in communication with anon-autonomous gateway 215 via a satellite 105, according to variousembodiments. The non-autonomous gateway 215 is in communication withother nodes of a non-routed ground segment network 220 (e.g., othernon-autonomous gateways 215) via one or more core nodes 265. Embodimentsof the satellite communications system 200 effectively provide mesh-likelayer-2 connectivity between substantially all the nodes of thenon-routed ground segment network 220.

In various embodiments, components of the non-routed ground segmentnetwork 220 (e.g., components of the gateways 115, core nodes 265, etc.)are implemented, in whole or in part, in hardware. They may include oneor more Application Specific Integrated Circuits (ASICs) adapted toperform a subset of the applicable functions in hardware. Alternatively,the functions may be performed by one or more other processing units, onone or more integrated circuits. In other embodiments, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays and other Semi-Custom ICs), which may beprogrammed. Each may also be implemented, in whole or in part, withinstructions embodied in a computer-readable medium, formatted to beexecuted by one or more general or application specific controllers.

In various embodiments, the satellite 105 is a geostationary satellite,configured to communicate with the user terminals 130 and gateways 115using reflector antennae, lens antennae, array antennae, phased arrayantennae, active antennae, or any other mechanism for reception of suchsignals. In some embodiments, the satellite 105 operates in a multi-beammode, transmitting a number of narrow beams, each directed at adifferent region of the earth. With such a multibeam satellite 105,there may be any number of different signal switching configurations onthe satellite 105, allowing signals from a single gateway 115 to beswitched between different spot beams. In one embodiment, the satellite105 is configured as a “bent pipe” satellite, wherein the satellite 105may frequency convert the received carrier signals before retransmittingthese signals to their destination, but otherwise perform little or noother processing on the contents of the signals. In various embodiments,there could be a single carrier signal or multiple carrier signals foreach service or feeder spot beam. In some embodiments, the subscriberantenna 135 and user terminal 130 together comprise a very smallaperture terminal (VSAT), with the subscriber antenna 135 measuring lessthan one meter in diameter and having approximately 2 watts of power. Inother embodiments, a variety of other types of subscriber antennae 135may be used at the user terminal 130 to receive the signal from thesatellite 105.

In certain embodiments, the satellite communications system 200 has itsnodes (e.g., non-autonomous gateways 215, core nodes 265, etc.)distributed over a large geographic region (e.g., across the UnitedStates of America). Each core node 265 may be configured to support upto twenty non-autonomous gateways 215, each non-autonomous gateway 215may be configured to support up to four user links, and each user linkmay support thousands of clients 160. For example, the satellite 105 mayoperate in a multi-beam mode, transmitting a number of spot beams, eachdirected at a different region of the earth. Each spot beam may beassociated with one of the user links, and used to communicate betweenthe satellite 105 and thousands of user terminals 130. With such amulti-beam satellite 105, there may be any number of different signalswitching configurations on the satellite 105, allowing signals from asingle gateway 115 to be switched between different spot beams.

In one illustrative case, a subscriber of satellite communicationsservices desires to access a web page using a browser. The subscriber'sclient 160 (e.g., a client application running on customer premisesequipment controlled by the subscriber) may communicate an HTML requestthrough a respective one of the user terminals 130. A user antenna 135in communication with the respective user terminal 130 communicates therequest to the satellite 105, which, in turn, sends the request to thenon-autonomous gateway 215 through a provider antenna 125.

The non-autonomous gateway 215 receives the request at a base station245 configured to service that user terminal 130 and included within asatellite modem termination system (SMTS) 240. Unlike in FIG. 1, wherethe SMTS 140 sends the request data to a routing module 150, the SMTS240 of FIG. 2 sends the request data to one or more layer-2 (L2)switches 247. The L2 switches 247 forward the data to a core node 265 orother node of the non-routed ground segment network 220 according tolayer-2 (e.g., or substantially equivalent) information. For example,unlike the router module 150 of FIG. 1, the L2 switches 247 may notexpend substantial resources analyzing higher layer tags (e.g., parsingIP headers) and may not strip off tags for the sake of packet routing.Furthermore, all terminals, code nodes, non-autonomous gateways,autonomous gateways, etc. are all able to be on a single contiguousnetwork.

In some embodiments, all data in the non-routed ground segment network220 being communicated between two non-autonomous gateways 215 passesthrough at least one core node 265. The core node 265 may include one ormore multilayer switches 250 and an gateway module 255. It is worthnoting that, while embodiments of the typical gateway 115 of FIG. 1 areshown to include gateway modules 155, embodiments of the non-autonomousgateways 215 do not include gateway modules 255. In some embodiments,the gateway module 255 of the core node 265 is substantially the same asthe gateway module 155 of FIG. 1.

When data is received at the core node 265 it may be processed in anumber of different ways by the one or more multilayer switches 250. Insome embodiments, the multilayer switches 250 process higher-layerinformation to provide certain types of functionality. For example, itmay be desirable to handle packets in certain ways according to virtualprivate networking (VPN) tags, voice-over-IP (VoIP) designations, and/orother types of higher-layer information.

It is worth noting that embodiments of the multilayer switches 250 areconfigured to process routing-types of information without strippingdata from the packets. In this way, embodiments of the satellitecommunications system 200 effectively provide mesh-like layer-2connectivity between substantially all the nodes of the non-routedground segment network 220. One feature of this type of layer-2connectivity is that embodiments may perform higher layer processingonly (e.g., or primarily) at the core nodes 265, which may substantiallyspeed up communications through the non-routed ground segment network220. Another feature is that embodiments of the non-routed groundsegment network 220 may allow certain types of information (e.g., VPLStags, proprietary network services tags, etc.) to persist acrossmultiple sub-networks. These and other features will be furtherappreciated from the description below.

In some embodiments, the layer-2 connectivity across the non-routedground segment network 220 is further enabled through the use of virtualtagging tuples. FIG. 3 shows an embodiment of a satellite communicationssystem 300 having a user terminal 130 in communication with anon-autonomous gateway 215 via a satellite 105, where the non-autonomousgateway 215 is further in communication with nodes of a non-routedground segment network 220 using virtual tagging tuples 375, accordingto various embodiments. As illustrated, the non-autonomous gateway 215is in communication with other nodes of the non-routed ground segmentnetwork 220 via a tuple-enabled communication link 370.

Embodiments of the tuple-enabled communication link 370 are configuredto carry traffic according to a virtual tagging tuple 375. The virtualtagging tuple 375 may be configured to have one or more elements thatvirtually define information about data relevant to communicating thedata through the non-routed ground segment network 220. In oneembodiment, the tuple-enabled communication link 370 is implemented as a10-Gigabit LAN PHY cable (an Ethernet cable configured according tocertain local area network (LAN) physical layer (PHY) standards).

Each virtual tagging tuple 375 may “reserve” or “carve out” a certainportion of the tuple-enabled communication link 370 (e.g., the fibertrunk). Each portion may be associated with (e.g., purchased by) anentity. For example, the tuple-enabled communication link 370 may bevirtually shared among a number of entities via the virtual taggingtuples 375, and the allotment for each entity may be based on the amountcarved out for the entity. For example, if the tuple-enabledcommunication link 370 represents ten Gigabits per second to “sell,”virtual tagging tuples 375 may be purchased in fractions of that linkcapacity (e.g., one-Gigabit increments). Each entity may then beserviced according to a quality of service structure or other servicelevel agreement, according to the capacity purchased. Further, eachentity may be provided with certain types of functionality associatedwith one or more of its virtual tagging tuples 375.

In one embodiment, the tuple-enabled communication link 370 is afiber-optic trunk configured according to IEEE Standard 802.1Q-2005(available athttp://standards.ieee.org/getieee802/download/802.1Q-2005.pdf). Eachvirtual tagging tuple 375 may be implemented as a “VLAN tag” accordingto the 802.1Q standard. For example, where the tuple has two elements,“double tagging,” or “Q-in-Q” tagging may be used according to the802.1Q standard.

For example, a request for content (e.g., an HTML page, a document file,a video file, an image file, etc.) is sent from a client 160 client to auser terminal 130. The request is transmitted up to the satellite 105and back down to the non-autonomous gateway 215 via the subscriberantenna 135 and the provider antenna 125. Components of thenon-autonomous gateway 215 (e.g., one or more L2 switches 247) areconfigured to add virtual tagging tuples 375 to the data packets.

The virtual tagging tuples 375 added to the data packets may include anentity designation and a location of the entity, implemented as anordered pair. For example, the entity may be “XYZ Corp,” with an entitydesignation of “205” (or some other numeric, alpha, or alphanumericdesignation). Furthermore, “XYZ Corp.” may be associated with any numberof locations. For example, “XYZ Corp.” may have locations in Denver,Colo., San Francisco, Calif., and Rapid City, S. Dak., and each of theselocations may be assigned a location identifier. For example, Denver,Colo. may be assigned “001,” San Francisco, Calif. may be assigned“360,” and Rapid City, S. Dak. may be assigned “101,” as their locationidentifiers. Accordingly, virtual tagging tuple 375 “(205, 001)” mayindicate traffic associated with “XYZ Corp.” and destined for Denver,Colo., while virtual tagging tuple 375 “(205, 101)” would indicatetraffic associated with “XYZ Corp.” and destined for Rapid City, S. Dak.

Additional entity designations may be generated. For example, “Co. A”may have a “D24” designation, while “Co. C” may have a “450”designation. Furthermore, location identifiers may be used by multipleentities. For example, virtual tagging tuple 375 “(D24, 360)” mayindicate traffic assigned to “Co. A” destined for San Francisco, Calif.,while virtual tagging tuple 375 “(205, 360)” indicates traffic assignedto “XYZ Corp.” also destined for San Francisco. Alternatively, eachentity my have its own customized location identifier(s).

In various embodiments of the non-routed ground segment network 220, thevirtual tagging tuples 375 are used to communicate the packetsthroughout the network without using port-based routing, destinationaddresses, header parsing, etc. The packets may effectively becommunicated among nodes of the non-routed ground segment network 220 asif the nodes are part of a single subnet. Even geographically remotenon-autonomous gateways 215 may communicate as if part of a local areanetwork (LAN). For example, as described above, based on virtual taggingtuple 375 entity and location designations, packets may be forwarded todesignated locations anywhere in the non-routed ground segment network220. The virtual tagging tuples 375 may be used by gateway modules,switches, cross-connects, core nodes, peering routers, and/or any othernode of the non-routed ground segment network 220.

In various embodiments, clients 160 may use the satellite communicationssystem 300 to communicate, via the non-routed ground segment network220, to any addressable location in communication with the non-routedground segment network 220. For example, clients 160 may communicatewith service providers, the Internet, content delivery networks (CDNs),other clients 160, etc. FIG. 4A shows an embodiment of a satellitecommunications system 400 used for communication between two clients 160over a non-routed ground segment network 220, according to variousembodiments. In some embodiments, the satellite communications system400 is substantially equivalent (e.g., an extended illustration of) thesatellite communications system 200 of FIG. 2.

A first client 160 a is in communication with a first non-autonomousgateway 215 a via a respective subscriber antenna 135 a and providerantenna 125, and the satellite 105. The first non-autonomous gateway 215a is in communication with one or more core nodes 265 (illustrated as afirst core node 265 a and an nth core node 265 n). For example, data iscommunicated from the first client 160 a, destined for a second client160 b. The data is received by a first base station 245 a in a firstSMTS 240 in the first non-autonomous gateway 215 a. The data is thenswitched by one or more first L2 switches 247 a and sent over a firstLAN PHY cable 370 a to one or more first multilayer switches 250 a inthe first core node 265 a. In the first core node 265 a, the data fromthe first client 160 a may be processed (e.g., interpreted, parsed,switched, etc.) at one or more layers by the first multilayer switches250 a and/or a first gateway module 255 a.

The first core node 265 a is in communication with at least a secondcore node 265 b. The first core node 265 a may determine, for example asa function of an associated virtual tagging tuple 375 or a higher-layertag, that the data from the first client 160 a should be passed to thesecond core node 265 b. The second core node 265 b may further processthe communications at one or more layers by second multilayer switches250 b and/or a second gateway module 255 b.

The second core node 265 b may pass the data to an appropriate secondnon-autonomous gateway 215 b, for example, over a second LAN PHY cable370 b. The second non-autonomous gateway 215 b may then switch the dataat layer 2 and pass the data to an appropriate second base station 245 bin a second SMTS 240 b in the second non-autonomous gateway 215 b. Forexample, the second base station 245 b is configured to support (e.g.,or is currently switched or tuned to support) a spot beam being used toservice the second client 160 b. The second base station 245 b maycommunicate the data from the second non-autonomous gateway 215 b to thesecond client 160 b via a respective provider antenna 125 b andsubscriber antenna 135 b, and the satellite 105.

It is worth noting that, while the first core node 265 a and/or thesecond core node 265 b may process the data at multiple layers,embodiments of the core nodes 265 are configured to maintain layer-2connectivity across the communication. In fact, the non-autonomousgateways 215, core nodes 265, and other nodes may all be part of anon-routed ground segment network (e.g., like the non-routed groundsegment network 220 of FIG. 2), and embodiments of the non-routed groundsegment network may effectuate layer-2 connectivity between any two ofits nodes. For example, the first non-autonomous gateway 215 a and thesecond non-autonomous gateway 215 b act as if they are on a singlesubnet (e.g., LAN), regardless of the number of nodes through which thedata passes, the distance over which it is communicated, the number ofsub-networks employed, etc.

It will be appreciated that a large non-routed ground segment networkmay include a number of different types of nodes, for example, toaccount for various client densities and locations, topologies (e.g.,mountain ranges, lakes, etc.), etc. Furthermore, satellitecommunications network 400 enables, for example, client 1 160 a andclient 2 160 b to function on the same network. As such, both clientsare able to have an IP address on the same sub-net (e.g., 192.168.1.*),receive the same services, receive a multicast or a broadcast message,etc. In other words, client 1 and client 2 are able to be connected inthe same manner similar to if were located in the same room connected tothe same switch.

Of course many of these features further involve use of one or moretypes of data stack throughout a communication link. For example, FIG.4B shows an illustrative communication link for an enterprise customerin a system in communication with an enterprise network 405, like theone shown in FIG. 4A, and FIG. 4C shows an illustrative data flowthrough the link in FIG. 4B. As illustrated, the communication link 450of FIG. 4B provides connectivity between enterprise customer premisesequipment (CPE) 160 and an enterprise head-end 405. Communications onthe communication link 450 may pass from the enterprise remote site to agateway 215 (e.g., from the CPE 160 to the gateway via a user terminaland a satellite link 105), from the gateway 215 to a core node 265(e.g., from an L2 backhaul switch in the gateway to an gateway and L2/L3switch in the core), and from the core to the enterprise head-end 405(e.g., from the L2/L3 switch in the core to a peer router in thehead-end via a leased line). The data flow 460 in FIG. 4C showsillustrative data stacks at various locations (410, 415, 420, and 425)in the communication link 450 of FIG. 4B. It is worth noting, forexample, that the bottom four layers of the illustrative data stackremains intact throughout the communication link 450.

As discussed above, the non-routed ground segment network (e.g., likethe network 400 of FIG. 4A) may include a number of different types ofnodes in various types of configurations. Some of these different typesof nodes and node configurations are described with reference to FIGS.5-9. Turning first to FIG. 5, an embodiment of a non-autonomous gateway215 is shown as part of a portion of a non-routed ground segment network220.

The non-autonomous gateway 215 includes a number of SMTSs 240.Embodiments of each SMTS 240 include multiple base stations. Forexample, each base station may be implemented on a circuit card or othertype of component integrates into the SMTS 240. The illustratednon-autonomous gateway 215 includes four STMSs 240, each incommunication with two L2 switches 247. For example, each SMTS 240 iscoupled with both L2 switches 247 to provide redundancy and/or otherfunctionality. Each L2 switch 247 may then be in communication (e.g.,directly or via other nodes of the non-routed ground segment network 220that are not shown) with one or more core nodes 265. For example, eachL2 switch 247 may be in communication with a single core node 265, sothat the non-autonomous gateway 215 is effectively in substantiallyredundant communication with two core nodes 265.

Embodiments of the non-autonomous gateway 215 are configured to supportother types of communication, for example, with other networks. In oneembodiment, one or more service providers are in communication with thenon-routed ground segment network 220 via one or both of the L2 switches247 or one or more of the core nodes 265. In one embodiment, thenon-autonomous gateway 215 includes an access router 560. The accessrouter 560 may be configured to interface with (e.g., provideconnectivity with) one or more out-of-band networks 570.

As described above, the L2 switches 247 in the non-autonomous gateway215 are in communication with one or more core nodes 265 so as tofacilitate persistent layer-2 connectivity. FIG. 6 shows an embodimentof a communications system 600 having multiple non-autonomous gateways215, like the non-autonomous gateway 215 of FIG. 5, in communicationwith a more detailed illustrative embodiment of a core node 265,according to various embodiments. As in FIG. 5, each non-autonomousgateway 215 includes multiple SMTSs 240, each in communication withmultiple L2 switches 247. Each L2 switch 247 is shown to be incommunication with a core node 265, so that the non-autonomous gateway215 is effectively in substantially redundant communication withmultiple core nodes 265. Further, in some embodiments, each core node265 is in communication with each other core node 265, either directlyor indirectly. For example, the core nodes 265 may be in communicationin a ring-like topology, a mesh-like topology, etc.

As discussed above, the non-autonomous gateways 215 communicate with thecore nodes 265 using layer-2 connectivity between one or more L2switches 247 in the non-autonomous gateways 215 and one or moremultilayer switches 250 in the core nodes 265. The illustrative firstcore node 265-1 is in communication with multiple non-autonomousgateways 215 via two multilayer switches 250. In various embodiments,the multilayer switches 250 are in communication with each other eitherdirectly or indirectly (e.g., via an gateway module 255).

In some embodiments, the gateway module 255 includes one or moreprocessing components for processing traffic received at the multilayerswitches 250. In one embodiment, the gateway module 255 includes atraffic shaper module 645. Embodiments of the traffic shaper module 645are configured to help optimize performance of the communications system600 (e.g., reduce latency, increase effective bandwidth, etc.), forexample, by delaying packets in a traffic stream to conform to one ormore predetermined traffic profiles.

The multilayer switches 250 may further be in communication with one ormore networks 605. The networks 605 may include the Internet 605 a, oneor more CDNs 605 b, one or more MPLS or VPLS networks 605 c, etc. Insome embodiments, the core node 265 includes an interface/peering node670 for interfacing with these networks 605. For example, an Internetservice provider or CDN service provider may peer with the core node 265via the interface/peering node 670.

Embodiments of the multilayer switches 250 process data by using one ormore processing modules in communication with the multilayer switches250. For example, as illustrated, the multilayer switches 250 may be incommunication with acceleration modules 650, provisioning modules 655,and/or management modules 660. Communications with some or all of thesemodules may be protected using components, like firewalls 665. Forexample, certain modules may have access to (and may use) privatecustomer data, proprietary algorithms, etc., and it may be desirable toinsulate that data from unauthorized external access. In fact, it willbe appreciated that many types of physical and/or logical security maybe used to protect operations and data of the core nodes 265. Forexample, each core node 265 may be located within a physically securedfacility, like a guarded military-style installation.

FIG. 7 shows embodiments of various modules in communication with one ormore multilayer switches 250, according to various embodiments. As inthe first core node 265-1 of FIG. 6, FIG. 7 shows multilayer switches250 in communication with acceleration modules 650, provisioning modules655, and management modules 660. The multilayer switches 250 are incommunication with the provisioning modules 655 and management modules660 via a firewall 665. It is worth noting that the illustrated modulesare intended only to show one non-limiting embodiment. Many other typesof modules, units, groupings, configurations, etc. are possibleaccording to other embodiments.

In one embodiment, the acceleration modules 650 include beam-specificacceleration modules 702 and a failover module 704 which detects aconnection failure and redirects network traffic to a backup orsecondary connection. Embodiments of the acceleration modules 650provide various types of application, WAN/LAN, and/or other accelerationfunctionality. In one embodiment, the acceleration modules 650 implementfunctionality of AcceleNet applications from Intelligent CompressionTechnologies, Inc. (“ICT”), a division of ViaSat, Inc. Thisfunctionality may be used to exploit information from higher layers ofthe protocol stack (e.g., layers 4-7 of the OSI stack) through use ofsoftware or firmware operating in each beam-specific acceleration module702. The acceleration modules 650 may provide high payload compression,which may allow faster transfer of the data and enhances the effectivecapacity of the network. In some embodiments, real-time types of data(e.g., User Datagram Protocol (UDP) data traffic) bypass theacceleration modules 650, while non-real-time types of data (e.g.,Transmission Control Protocol (TCP) data traffic) are routed through theaccelerator module 350 for processing. For example, IP televisionprogramming may bypass the acceleration modules 650, while web video maybe sent to the acceleration modules 650 from the multilayer switches250.

In one embodiment, the provisioning modules 655 include a AAA/Radiusmodule 712, a DHCP/DNS module 714, a TFTP/NTP module 716, and a PKImodule 718. Embodiments of the AAA/Radius module 712 perform certaintypes of authentication and accounting functionality. For example, theAAA/Radius module 712 may implement functionality of an AuthenticationAuthorization Accounting (AAA) server, a Remote Authentication Dial-InUser Service (RADIUS) protocol, an Extensible Authentication Protocol(EAP), a network access server (NAS), etc. Embodiments of the DHCP/DNSmodule 714 implement various IP management functions, including DynamicHost Configuration Protocol (DHCP) interpretation, Domain Name System(DNS) look-ups and translations, etc. Embodiments of the TFTP/NTP module716 implement various types of protocol-based functions, including filetransfer protocols (e.g., File Transfer Protocol (FTP), trivial filetransfer protocol (TFTP), etc.), synchronization protocols (e.g.,Network Time Protocol (NTP)), etc. Embodiments of the PKI module 718implement various types of encryption functionality, includingmanagement of Public Key Infrastructures (PKIs), etc.

In one embodiment, the management modules 660 include anauthentication/accounting module 722, a terminal/shell module 724, apacket analysis module 726, an SNMP/Syslog module 728, etc. Embodimentsof the authentication/accounting module 722 implement variousauthentication and accounting functions that may be similar to ordifferent from those of the AAA/Radius module 712. For example, theauthentication/accounting module 722 may control certain billingfunctions, handle fair access policies (FAPs), etc. Embodiments of theterminal/shell module 724 implement various types of connectivity withindividual devices. Embodiments of the packet analysis module 726implement various packet analysis functions. For example, the packetanalysis module 726 may collect packet-level information and/orstatistics for use in certain types of accounting functions. Embodimentsof the SNMP/Syslog module 728 implement various network protocolmanagement and logging functions. For example, the SNMP/Syslog module728 may use the Simple Network Management Protocol (SNMP) to exposenetwork management information and the Syslog standard to log networkmessages.

It is worth noting that the functionality of the various modules isdescribed as occurring within one or more core modules 265, and the coremodules are in communication with a distributed network ofnon-autonomous gateways 115 and/or other nodes. While this type ofdistributed non-routing networking may be preferred in manyenvironments, it may be difficult (e.g., not cost-effective ortechnologically inefficient) or impractical for a gateway to communicatewith a core node 265. As such, it may be desirable in some environmentsto implement a so-called autonomous gateway having at least some of thecombined functionality of a non-autonomous gateway 215 and a core node265.

FIG. 8 shows an embodiment of an autonomous gateway 815, according tovarious embodiments. In some embodiments, the autonomous gateway 815includes one or more SMTSs 240, which may be implements substantially asthe SMTSs 240 of the non-autonomous gateway 215 of FIG. 2. The SMTSs 240may be in communication with one or more multilayer switches 250. Themultilayer switches 250 may be in communication with a gateway module255 and an interface/peering node 670. The interface/peering node 670may be in communication with one or more other networks 605. It is worthnoting that the gateway module 255 may include other functionality incertain embodiments. For example, the illustrated embodiment includes atraffic shaper module 645. In other embodiments, the traffic shapermodule 645 may be implemented differently or as part of a differentcomponent. The multilayer switches 250 may be configured to process datausing one or more modules. For example, the multilayer switches 250 maybe in communication with acceleration modules 650, provisioning modules655, and/or management modules 660, for example, through one or morefirewalls 665. It will be appreciated that, unlike the typical gateway115 of FIG. 1, in accordance with aspects of the present invention,embodiments of the autonomous gateway are able to implement some of theenhanced (e.g., Layer-2 connectivity-enabled) functionality of thenon-autonomous gateways 215 and core nodes 265.

FIG. 9 shows an embodiment of a satellite communications system 900 thatdistributes autonomous gateways 815 and non-autonomous gateways 215across a number of geographically dispersed regions 905, according tovarious embodiments. In one embodiment, a first geographic region 905 a,a second geographic region 905 b and a sixth geographic region 905 frepresent environments where it is not cost-effective to providecommunications with core nodes 265. As such, these geographic regions905 are illustrated as having autonomous gateways 815. For example,autonomous gateways 815 may be used in island regions, geographicallyremote regions, regions with particular types of topologies (e.g., largemountain ranges), etc.

In contrast to the above-mentioned regions (geographic regions 905 a,905 b, and 905 f), a third geographic region 905 c, a fourth geographicregion 905 d, and a fifth geographic region 905 e indicate regions whereit is cost-effective to implement a core-based non-routed ground segmentnetwork 220. As illustrated, each non-autonomous gateway 215 is eitherdirectly or indirectly in communication with at least one core node 265(e.g., typically two core nodes 265). Other components may also beincluded in the non-routed ground segment network 220. For example,additional switches 910, optical cross-connects 920, etc. may be used.Further, while the non-routed ground segment network 220 is configuredto provide point-to-point layer-2 connectivity, other types ofconnectivity may also be implemented between certain nodes. For example,one or more VPLS networks may be implemented to connect certain nodes ofthe non-routed ground segment network 220.

In various embodiments, core nodes 265 may be located on a new orexisting fiber run, for example, between metropolitan areas. In someconfigurations, the core nodes 265 may be located away from the majorityof spot beams (e.g., in the middle of the country, where much of thesubscriber population lives closer to the outsides of the country). Inalternative embodiments, core nodes 265 may be located near the majorityof spot means. Such spatial diversity between code nodes and subscriberterminals may, for example, facilitate frequency re-use of betweenservice beams and feeder beams. Similarly, non-autonomous gateways 215may be located to account for these and/or other considerations.

It is worth noting that, in the non-routed ground segment network 220,twelve gateways (e.g., including both non-autonomous gateways 215 andautonomous gateways 815) are illustrated. If all were implemented asautonomous gateways 815, the topology may require twelve gatewaymodules, routers, switches, and other hardware components. Further,various licensing and/or support services may have to be purchased foreach of the autonomous gateways 815. In some cases, licensingrequirements may dictate a minimum purchase of ten thousand licenses foreach gateway module, which may require an initial investment into120-thousand licenses from the first day of operation.

Using aggregated functionality in one or more core nodes 265, however,may minimize some of these issues. For example, the non-routed groundsegment network 220 includes four core nodes 265, each having a gatewaymodule, and only three of the twelve gateways are autonomous gateways815. As such, only seven gateway modules may be operating on thenon-routed ground segment network 220. As such, only seven instances ofeach core networking component may be needed, only seven licenses may beneeded, etc. This may allow for a softer ramp-up and other features.

FIG. 10 shows an illustrative flow diagram of a method of implementingaccess node/gateway to access node/gateway layer-2 connectivity within abackhaul ground segment network connected to one or more satellites. Atprocess block 1005, data packets may be transmitted form a firstsatellite to a first base station. The first base station may thengenerate virtual tagging tuples to include in the layer-2 header(process block 1010).

Furthermore, the first base station then transmits the virtually taggedpackets to a first switch (process block 1015), and the first switchtransmits the packets to a second switch (process block 1020). Then, atprocess block 1025, the second switch transmits the packets to a secondbase station which determines, based on the virtual tagging tuple, theentity and destination of the packets (process block 1030).

FIG. 11 is a simplified block diagram illustrating the physicalcomponents of a computer system 1100 that may be used in accordance withan embodiment of the present invention. This diagram is merely anexample, which should not unduly limit the scope of the claims. One ofordinary skill in the art would recognize many variations, alternatives,and modifications.

In various embodiments, computer system 1100 may be used to implementany of the computing devices of the present invention. As shown in FIG.11, computer system 1100 comprises hardware elements that may beelectrically coupled via a bus 1124. The hardware elements may includeone or more central processing units (CPUs) 1102, one or more inputdevices 1104 (e.g., a mouse, a keyboard, etc.), and one or more outputdevices 1106 (e.g., a display device, a printer, etc.). For example, theinput devices 1104 are used to receive user inputs for procurementrelated search queries. Computer system 1100 may also include one ormore storage devices 1108. By way of example, storage devices 1108 mayinclude devices such as disk drives, optical storage devices, andsolid-state storage devices such as a random access memory (RAM) and/ora read-only memory (ROM), which can be programmable, flash-updateableand/or the like. In an embodiment, various databases are stored in thestorage devices 1108. For example, the central processing unit 1102 isconfigured to retrieve data from a database and process the data fordisplaying on a GUI.

Computer system 1100 may additionally include a computer-readablestorage media reader 1112, a communications subsystem 1114 (e.g., amodem, a network card (wireless or wired), an infra-red communicationdevice, etc.), and working memory 1118, which may include RAM and ROMdevices as described above. In some embodiments, computer system 1100may also include a processing acceleration unit 1116, which can includea digital signal processor (DSP), a special-purpose processor, and/orthe like.

Computer-readable storage media reader 1112 can further be connected toa computer-readable storage medium 1110, together (and, optionally, incombination with storage devices 1108) comprehensively representingremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containingcomputer-readable information. Communications system 1114 may permitdata to be exchanged with network and/or any other computer.

Computer system 1100 may also comprise software elements, shown as beingcurrently located within working memory 1118, including an operatingsystem 1120 and/or other code 1122, such as an application program(which may be a client application, Web browser, mid-tier application,RDBMS, etc.). In a particular embodiment, working memory 1118 mayinclude executable code and associated data structures for one or moreof design-time or runtime components/services. It should be appreciatedthat alternative embodiments of computer system 1100 may have numerousvariations from that described above. For example, customized hardwaremight also be used and/or particular elements might be implemented inhardware, software (including portable software, such as applets), orboth. Further, connection to other computing devices such as networkinput/output devices may be employed. In various embodiments, thebehavior of the view functions described throughout the presentapplication is implemented as software elements of the computer system1100.

In one set of embodiments, the techniques described herein may beimplemented as program code executable by a computer system (such as acomputer system 1100) and may be stored on machine-readable media.Machine-readable media may include any appropriate media known or usedin the art, including storage media and communication media, such as(but not limited to) volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageand/or transmission of information such as machine-readableinstructions, data structures, program modules, or other data, includingRAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disk (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store ortransmit the desired information and which can be accessed by acomputer.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure. Further, while theinvention has been described with respect to exemplary embodiments, oneskilled in the art will recognize that numerous modifications arepossible. For example, the methods and processes described herein may beimplemented using hardware components, software components, and/or anycombination thereof. Further, while various methods and processesdescribed herein may be described with respect to particular structuraland/or functional components for ease of description, methods of theinvention are not limited to any particular structural and/or functionalarchitecture but instead can be implemented on any suitable hardware,firmware and/or software configuration. Similarly, while variousfunctionality is ascribed to certain system components, unless thecontext dictates otherwise, this functionality can be distributed amongvarious other system components in accordance with different embodimentsof the invention.

Moreover, while the procedures comprised in the methods and processesdescribed herein are described in a particular order for ease ofdescription, unless the context dictates otherwise, various proceduresmay be reordered, added, and/or omitted in accordance with variousembodiments of the invention. Moreover, the procedures described withrespect to one method or process may be incorporated within otherdescribed methods or processes; likewise, system components describedaccording to a particular structural architecture and/or with respect toone system may be organized in alternative structural architecturesand/or incorporated within other described systems. Hence, while variousembodiments are described with—or without—certain features for ease ofdescription and to illustrate exemplary features, the various componentsand/or features described herein with respect to a particular embodimentcan be substituted, added and/or subtracted from among other describedembodiments, unless the context dictates otherwise. Consequently,although the invention has been described with respect to exemplaryembodiments, it will be appreciated that the invention is intended tocover all modifications and equivalents within the scope of thefollowing claims.

1. A system for providing end-to-end layer-2 connectivity throughout anon-routed ground segment network connected to one or more satellites,the system comprising: one or more satellites configured to transmitdata packets; a first non-autonomous gateway in communication with theone or more satellites, the first non-autonomous gateway configured toreceive the data packets from the one or more satellites at layer-1 (L1)of the OSI-model, generate a plurality of virtual tagging tuples withinthe layer-2 (L2) packet headers of the data packets, wherein pluralityof data packets each including a virtual tagging tuple; a L2 switch incommunication with the first non-autonomous gateway, the L2 switchconfigured to receive the plurality of virtually tagged data packets andtransmit the plurality of virtually tagged data packets; and a secondnon-autonomous gateway in communication with the L2 switch, the secondnon-autonomous gateway configured to receive the plurality of virtuallytagged data packets and to transmit the plurality of virtually taggeddata packets to an entity based on the virtual tagging tuple associatedwith each of the plurality of virtually tagged packets.
 2. A system forproviding end-to-end layer-2 connectivity throughout a non-routed groundsegment network connected to one or more satellites as in claim 1,wherein the first and second non-autonomous gateways comprise a gatewaymodule.
 3. A system for providing end-to-end layer-2 connectivitythroughout a non-routed ground segment network connected to one or moresatellites as in claim 1, wherein the first and second non-autonomousgateways comprise access points.
 4. A system for providing end-to-endlayer-2 connectivity throughout a non-routed ground segment networkconnected to one or more satellites as in claim 1, wherein the first andsecond non-autonomous gateways are coupled with the L2 switch via aniEEE 802.1Q fiber trunk.
 5. A system for providing end-to-end layer-2connectivity throughout a non-routed ground segment network connected toone or more satellites as in claim 4, wherein the plurality of virtualtuples designate at least one stand of the iEEE 802.1Q trunk fiber.
 6. Asystem for providing end-to-end layer-2 connectivity throughout anon-routed ground segment network connected to one or more satellites asin claim 1, further comprising a user terminal coupled with the one ormore satellites, wherein the user terminal is configured to transmitdata packets to the one or more satellites and to receive data packetsfrom the one or more satellites.
 7. A system for providing end-to-endlayer-2 connectivity throughout a non-routed ground segment networkconnected to one or more satellites as in claim 6, further comprising aplurality of clients in communication with the use terminal.
 8. A systemfor providing end-to-end layer-2 connectivity throughout a non-routedground segment network connected to one or more satellites as in claim6, wherein the first and second non-autonomous gateways are coupled withthe user terminal via a LAN PHY connection.
 9. A system for providingend-to-end layer-2 connectivity throughout a non-routed ground segmentnetwork connected to one or more satellites as in claim 1, wherein theplurality of virtual tagging tuples are configured to designate theentity and a location of the entity.
 10. A method of providingend-to-end layer-2 connectivity throughout a non-routed ground segmentnetwork connected to one or more satellites, the method comprising:transmitting, by the one or more satellites, data packets; receiving, ata first non-autonomous gateway in communication with the one or moresatellites, the data packets from the one or more satellites at layer-1(L1) of the OSI-model; generating, by the first non-autonomous gateway,a plurality of virtual tagging tuples within the layer-2 (L2) packetheaders of the data packets, wherein the plurality of data packets eachinclude a virtual tagging tuple; receiving, at a L2 switch incommunication with the first non-autonomous gateway, the plurality ofvirtually tagged data packets; transmitting, by the L2 switch, theplurality of virtually tagged data packets; receiving, by a secondnon-autonomous gateway in communication with the L2 switch, theplurality of virtually tagged data packets; and transmitting, by thesecond non-autonomous gateway, the plurality of virtually tagged datapackets to an entity based on the virtual tagging tuple associated witheach of the plurality of virtually tagged packets.
 11. A method ofproviding end-to-end layer-2 connectivity throughout a non-routed groundsegment network connected to one or more satellites as in claim 10,wherein the plurality of virtual tuples designate at least one stand ofthe iEEE 802.1Q trunk fiber.
 12. A method of providing end-to-endlayer-2 connectivity throughout a non-routed ground segment networkconnected to one or more satellites as in claim 10, further comprisingdesignating, using the virtual tagging tuples, the entity and a locationof the entity.
 13. A method of providing end-to-end layer-2 connectivitythroughout a non-routed ground segment network connected to one or moresatellites as in claim 12, wherein the location of the entity comprisesa branch office of the entity.
 14. A method of providing end-to-endlayer-2 connectivity throughout a non-routed ground segment networkconnected to one or more satellites as in claim 10, wherein theconnectivity between the first non-autonomous gateway and the secondnon-autonomous gateway is at L2.
 15. A method of providing end-to-endlayer-2 connectivity throughout a non-routed ground segment networkconnected to one or more satellites as in claim 10, wherein the firstnon-autonomous gateway and the second non-autonomous gateway are incommunication with a core node at L2.
 16. A computer-readable mediumhaving sets of instructions stored thereon which, when executed by oneor more computers, cause the one or more computers to: transmit, by theone or more satellites, data packets; receive, at a first non-autonomousgateway in communication with the one or more satellites, the datapackets from the one or more satellites at layer-1 (L1) of theOSI-model; generate, by the first non-autonomous gateway, a plurality ofvirtual tagging tuples within the layer-2 (L2) packet headers of thedata packets, wherein the plurality of data packets each include avirtual tagging tuple; receive, at a L2 switch in communication with thefirst non-autonomous gateway, the plurality of virtually tagged datapackets; transmit, by the L2 switch, the plurality of virtually taggeddata packets; receive, by a second non-autonomous gateway incommunication with the L2 switch, the plurality of virtually tagged datapackets; and transmit, by the second non-autonomous gateway, theplurality of virtually tagged data packets to an entity based on thevirtual tagging tuple associated with each of the plurality of virtuallytagged packets.
 17. A computer-readable medium as in claim 16, whereinthe sets of instructions when further executed by the one or morecomputers, cause the one or more computers to designate, using thevirtual tagging tuples, the entity and a location of the entity.
 18. Acomputer-readable medium as in claim 16, wherein the plurality ofvirtual tuples designate at least one stand of the iEEE 802.1Q trunkfiber.
 19. A computer-readable medium as in claim 16, wherein the setsof instructions when further executed by the one or more computers,cause the one or more computers to transmit data packets from a userterminal to the one or more satellites and receive data packets from theone or more satellites.
 20. A computer-readable medium as in claim 16,wherein the first and second non-autonomous gateways are coupled withthe user terminal via a LAN PHY connection.